CVE-2026-31737
net: ftgmac100: fix ring allocation unwind on open failure
Description
In the Linux kernel, the following vulnerability has been resolved: net: ftgmac100: fix ring allocation unwind on open failure ftgmac100_alloc_rings() allocates rx_skbs, tx_skbs, rxdes, txdes, and rx_scratch in stages. On intermediate failures it returned -ENOMEM directly, leaking resources allocated earlier in the function. Rework the failure path to use staged local unwind labels and free allocated resources in reverse order before returning -ENOMEM. This matches common netdev allocation cleanup style.
INFO
Published Date :
May 1, 2026, 3:16 p.m.
Last Modified :
May 7, 2026, 6:55 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Update the Linux kernel to include the fix.
- Ensure proper resource cleanup on allocation errors.
- Apply patches for net: ftgmac100 driver.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-31737.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-31737 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-31737
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-31737 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-31737 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
May. 07, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Added CWE NVD-CWE-noinfo Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.203 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.22 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.168 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 6.19.12 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.81 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.134 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.12 up to (excluding) 5.10.253 Added Reference Type kernel.org: https://git.kernel.org/stable/c/184b3a500d60ea48d1b176103cff1706c456edf3 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/78da43320d9d6ed788147fb085184e4fc801f057 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/82f86111f0704ab2ded11a2033bc6cf0be3e09ea Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/8351d18989c8642fc53e2e12d94e42314a39b078 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/8a71911fc7eeea930153322bc1efc065db8cd97e Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/a7e1bf392acf11dc4209820fef75758f6e42bd65 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/c0fd0fe745f5e8c568d898cd1513d0083e46204a Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/d45230081f19c280096241353c26b0de457de795 Types: Patch -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 01, 2026
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: net: ftgmac100: fix ring allocation unwind on open failure ftgmac100_alloc_rings() allocates rx_skbs, tx_skbs, rxdes, txdes, and rx_scratch in stages. On intermediate failures it returned -ENOMEM directly, leaking resources allocated earlier in the function. Rework the failure path to use staged local unwind labels and free allocated resources in reverse order before returning -ENOMEM. This matches common netdev allocation cleanup style. Added Reference https://git.kernel.org/stable/c/184b3a500d60ea48d1b176103cff1706c456edf3 Added Reference https://git.kernel.org/stable/c/78da43320d9d6ed788147fb085184e4fc801f057 Added Reference https://git.kernel.org/stable/c/82f86111f0704ab2ded11a2033bc6cf0be3e09ea Added Reference https://git.kernel.org/stable/c/8351d18989c8642fc53e2e12d94e42314a39b078 Added Reference https://git.kernel.org/stable/c/8a71911fc7eeea930153322bc1efc065db8cd97e Added Reference https://git.kernel.org/stable/c/a7e1bf392acf11dc4209820fef75758f6e42bd65 Added Reference https://git.kernel.org/stable/c/c0fd0fe745f5e8c568d898cd1513d0083e46204a Added Reference https://git.kernel.org/stable/c/d45230081f19c280096241353c26b0de457de795